-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
staging-next 2024-08-06 #332764
staging-next 2024-08-06 #332764
Conversation
The hook relied on the `test` command passed to `setup.py`, which has long been deprecated and finally removed in setuptools 72.0.
The source is also reused in pytest-server-fixtures, pytest-shutil and pytest-virtualenv, which now inherit the patch.
These tests have forced the hydra job for electrum-ltc to run into a timeout.
Accessing packaging via setuptools.extern is dead.
Depending on aiohttp yields an infinite recursion.
Requests in 2.32.3 caused a regression in the code path that loads the default certificate authorities, breaking downstream consumers like httpie in the process. The patch series fixing this is currently still a draft, since tests are missing, but it at least fixes the reproducer and httpie.
home-assistant: support imgw_pib component
add python to nativeBuildInputs to fix build
This reverts commit 0df677d. This was reverted on master, but the the fixes had already landed on staging-next, so it shouldn't have been revert here.
[staging-next] qt6.qtdeclarative: slightly less bad hack to make it build on Darwin again
python311Packages.example-robot-data: fix strict deps
Conflicts: - pkgs/top-level/python-packages.nix
...into staging-next
After this merge awscli2-2.17.18 build started to fail
|
This is normal for staging cycles. Not every regression can be addressed in a reasonable time. |
awscli2 fixed #334858 |
It seems like the periodic merges master -> staging-next, staging-next -> staging. Are somehow happening in my name. See e.g. here: https://github.com/NixOS/nixpkgs/actions/runs/10489420359 I currently get one alert every 6h because staging-next -> staging gives a merge conflict. I think this has been going on for ages, but I recently changed the way I engage with GitHub notifications and now this alerts are a bit annoying to me. According to this help article https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/notifications-for-workflow-runs If anyone is interested in receiving these alerts, then according to the above help article they need to disable and reenable the workflow in the GitHub ui, making them the "actor" of the workflow. Otherwise I am trying to figure out how to silence them for me, but I am not completely optimistic that I can. |
Yeah, as far as I can tell, I can just disable workflow notifications globally for all of GitHub which would not make my employer happy. So if anyone would be willing to take this from me, because they either deal with staging more than I do or because they don’t care much about GitHub notifications anyway, I would be very thankful. |
Helpful links
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
https://hydra.nixos.org/job/nixos/staging-next-small/tested
https://hydra.nixos.org/jobset/nixpkgs/staging-next
https://hydra.nixos.org/jobset/nixos/staging-next-small
Mass breakages
nothing notable so far